Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce6fe006f74870fbbd4e51e879e8ab0053211b5fcfb87e7a4d4588547b79cac4

Tx prefix hash: fc03856f2b81e1d4b489ecf09b2e29b283af3b0fa3d8e1cf949466adafd22d8b
Tx public key: fe45ae32bc0ca39b7d26b557b8c868de403c75bc2b528f22deae35aed2d04316
Timestamp: 1718015333 Timestamp [UCT]: 2024-06-10 10:28:53 Age [y:d:h:m:s]: 00:228:13:16:24
Block: 1041107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163508 RingCT/type: yes/0
Extra: 01fe45ae32bc0ca39b7d26b557b8c868de403c75bc2b528f22deae35aed2d043160211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af37c4ac574fce701693152855bb94aaa85e029cd7f2f5f2cc4805599461dc59 0.600000000000 1509772 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": 1041117, "vin": [ { "gen": { "height": 1041107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af37c4ac574fce701693152855bb94aaa85e029cd7f2f5f2cc4805599461dc59" } } ], "extra": [ 1, 254, 69, 174, 50, 188, 12, 163, 155, 125, 38, 181, 87, 184, 200, 104, 222, 64, 60, 117, 188, 43, 82, 143, 34, 222, 174, 53, 174, 210, 208, 67, 22, 2, 17, 0, 0, 0, 1, 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