Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82e5db71f7fa6e5d88ae495df23ab986924c45d60681a34edab818ef425a753

Tx prefix hash: c808aea2d6aefbf4e3de4cf96b7fbe511f99dffe3f31acc9d375c50c700670e2
Tx public key: 9a2682ed0b47e901212f3fdced0033cff6c8c40ff5ee4d1e5b698378377e874d
Timestamp: 1714721313 Timestamp [UCT]: 2024-05-03 07:28:33 Age [y:d:h:m:s]: 01:021:14:56:36
Block: 1013802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276391 RingCT/type: yes/0
Extra: 019a2682ed0b47e901212f3fdced0033cff6c8c40ff5ee4d1e5b698378377e874d0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362db2fc12717eabc04542cf4526a0ebdf44025b462db9c947577b5fde3b5661 0.600000000000 1476715 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": 1013812, "vin": [ { "gen": { "height": 1013802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362db2fc12717eabc04542cf4526a0ebdf44025b462db9c947577b5fde3b5661" } } ], "extra": [ 1, 154, 38, 130, 237, 11, 71, 233, 1, 33, 47, 63, 220, 237, 0, 51, 207, 246, 200, 196, 15, 245, 238, 77, 30, 91, 105, 131, 120, 55, 126, 135, 77, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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