Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d09f476c0c7627f6377fc97875f597b31e263e80a4804a190d1e37a26109e9

Tx prefix hash: 0ad1d16104c8d7f050f6b20f4792699bdd65e4bc29eb6f88de18b0338efbaa84
Tx public key: e8363f3fa7399b5620ab37d4f2f814196b41474c5ad41e8a05c4b635ddbfde7f
Timestamp: 1727941556 Timestamp [UCT]: 2024-10-03 07:45:56 Age [y:d:h:m:s]: 00:184:15:51:36
Block: 1123399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131768 RingCT/type: yes/0
Extra: 01e8363f3fa7399b5620ab37d4f2f814196b41474c5ad41e8a05c4b635ddbfde7f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66cbea059ac431626f0cbf7acab70c8bc4c4c17a3d83e392d61a53726d1b96a0 0.600000000000 1605932 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": 1123409, "vin": [ { "gen": { "height": 1123399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66cbea059ac431626f0cbf7acab70c8bc4c4c17a3d83e392d61a53726d1b96a0" } } ], "extra": [ 1, 232, 54, 63, 63, 167, 57, 155, 86, 32, 171, 55, 212, 242, 248, 20, 25, 107, 65, 71, 76, 90, 212, 30, 138, 5, 196, 182, 53, 221, 191, 222, 127, 2, 17, 0, 0, 0, 3, 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