Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1a947a77acf30ce70e007f4790d2ee36215d6d8d26362693d60c617eb0f2d9e8

Tx prefix hash: 067433484a4e80f5582f755e0e3cb5d2f09c26660e898d4dd409eccf8de72bee
Tx public key: 57f2067c1ca148fb3635ab2f9e1f45f50369c7d404b8cf804ee91b5179748d4d
Timestamp: 1696527425 Timestamp [UCT]: 2023-10-05 17:37:05 Age [y:d:h:m:s]: 01:102:04:50:25
Block: 863156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334309 RingCT/type: yes/0
Extra: 0157f2067c1ca148fb3635ab2f9e1f45f50369c7d404b8cf804ee91b5179748d4d02110000000333af99f4000000000000000000

1 output(s) for total of 0.847238917000 dcy

stealth address amount amount idx
00: fd6b60e309faa5a732a714ebfede2aa9be9a6b2c0fd7acdd77ccab806f1dc367 0.847238917000 1317604 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 863166, "vin": [ { "gen": { "height": 863156 } } ], "vout": [ { "amount": 847238917, "target": { "key": "fd6b60e309faa5a732a714ebfede2aa9be9a6b2c0fd7acdd77ccab806f1dc367" } } ], "extra": [ 1, 87, 242, 6, 124, 28, 161, 72, 251, 54, 53, 171, 47, 158, 31, 69, 245, 3, 105, 199, 212, 4, 184, 207, 128, 78, 233, 27, 81, 121, 116, 141, 77, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8