Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87b34f0cbdc6278360dc9c6c7f61bfd162c92c49341c943652bedcc5da684338

Tx prefix hash: 447424e487973aa8b96096c86a8150e601e74798c4257b8a0447c5ac140e258c
Tx public key: 3a8a3fa4759d4931b83624f83e34ff9ec8dfe027e96ea09c67ef7d61f33571dd
Timestamp: 1697724224 Timestamp [UCT]: 2023-10-19 14:03:44 Age [y:d:h:m:s]: 01:147:03:08:47
Block: 873081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366183 RingCT/type: yes/0
Extra: 013a8a3fa4759d4931b83624f83e34ff9ec8dfe027e96ea09c67ef7d61f33571dd02110000000f75e3f0e9000000000000000000

1 output(s) for total of 0.785453061000 dcy

stealth address amount amount idx
00: 302e2d6a75b2586b3e1a19651503a51704ada116cfb0c0514ce5482db3f611bd 0.785453061000 1328201 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": 873091, "vin": [ { "gen": { "height": 873081 } } ], "vout": [ { "amount": 785453061, "target": { "key": "302e2d6a75b2586b3e1a19651503a51704ada116cfb0c0514ce5482db3f611bd" } } ], "extra": [ 1, 58, 138, 63, 164, 117, 157, 73, 49, 184, 54, 36, 248, 62, 52, 255, 158, 200, 223, 224, 39, 233, 110, 160, 156, 103, 239, 125, 97, 243, 53, 113, 221, 2, 17, 0, 0, 0, 15, 117, 227, 240, 233, 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