Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65af2fc7267fc4a260043317295fe1b46ddd1cfe5d04a34c27f48cc0b3800c8

Tx prefix hash: 8a84beeec4ed66263fd5d0b529dfeed63660fce1e221e080a31b5eb21e43d364
Tx public key: d2212ed49e1f888c7c133256b5cb210c0a84fcef1bcbb7285383db523a580e85
Timestamp: 1737807384 Timestamp [UCT]: 2025-01-25 12:16:24 Age [y:d:h:m:s]: 00:048:03:46:33
Block: 1204991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34241 RingCT/type: yes/0
Extra: 01d2212ed49e1f888c7c133256b5cb210c0a84fcef1bcbb7285383db523a580e85021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f55dff989640022d9f6a3df66b3d5ce8103eb85a4b68ea9effc5815aeb73f6ad 0.600000000000 1691686 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": 1205001, "vin": [ { "gen": { "height": 1204991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f55dff989640022d9f6a3df66b3d5ce8103eb85a4b68ea9effc5815aeb73f6ad" } } ], "extra": [ 1, 210, 33, 46, 212, 158, 31, 136, 140, 124, 19, 50, 86, 181, 203, 33, 12, 10, 132, 252, 239, 27, 203, 183, 40, 83, 131, 219, 82, 58, 88, 14, 133, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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