Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9349ae1c86c03187dd1c412765fa825b2e4fdf33c3af8f558f4a9f0e68eaa389

Tx prefix hash: 45bccf0b2f0edb0e2c4e6b565b6d8bcd9794601e224f08f49d634b802ecdfc84
Tx public key: 64e4d8c8ceac34ad16b22b0997a7a8e4b7e0479e7bd9b5adce50a720e9cdc2d1
Timestamp: 1720886430 Timestamp [UCT]: 2024-07-13 16:00:30 Age [y:d:h:m:s]: 00:267:11:24:26
Block: 1064916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191068 RingCT/type: yes/0
Extra: 0164e4d8c8ceac34ad16b22b0997a7a8e4b7e0479e7bd9b5adce50a720e9cdc2d1021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 552d741037900c01869697baab301a9bd3410e7fecfddd656f704bc11997b910 0.600000000000 1535457 of 15

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": 1064926, "vin": [ { "gen": { "height": 1064916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552d741037900c01869697baab301a9bd3410e7fecfddd656f704bc11997b910" } } ], "extra": [ 1, 100, 228, 216, 200, 206, 172, 52, 173, 22, 178, 43, 9, 151, 167, 168, 228, 183, 224, 71, 158, 123, 217, 181, 173, 206, 80, 167, 32, 233, 205, 194, 209, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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