Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfde8cc0e6f0fdea0ac80f349f28c57c10e5fbeace12c54ed0204011609753c5

Tx prefix hash: 71df216b9055747a1b4ea906692a0da900e9ec9c93a758666b6d45be39a6e48d
Tx public key: 9c230f401aeeb67610c778666d39d25d338acb52141f243ae5b7bf0a829254cf
Timestamp: 1763863279 Timestamp [UCT]: 2025-11-23 02:01:19 Age [y:d:h:m:s]: 00:030:15:56:25
Block: 1418072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21963 RingCT/type: yes/0
Extra: 019c230f401aeeb67610c778666d39d25d338acb52141f243ae5b7bf0a829254cf02110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5cbc505a113fe8f078c483c1e716b6bfb0dfafe43df54638fdee9aea12234e 0.600000000000 1906599 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": 1418082, "vin": [ { "gen": { "height": 1418072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5cbc505a113fe8f078c483c1e716b6bfb0dfafe43df54638fdee9aea12234e" } } ], "extra": [ 1, 156, 35, 15, 64, 26, 238, 182, 118, 16, 199, 120, 102, 109, 57, 210, 93, 51, 138, 203, 82, 20, 31, 36, 58, 229, 183, 191, 10, 130, 146, 84, 207, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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