Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9118da0ec4a4fde3c23d4341a7db807888ee13fb113d9f4890dfaa5b033b5f43

Tx prefix hash: 42ecba3188fa77903fd66ab9aba62890f94fc9c766f4256e67c41cab36b0ec9a
Tx public key: 2d47c8552f3576a8fcc05c1faf671c1d8613c76d4219e874b55a1cc80bfbc794
Timestamp: 1717547097 Timestamp [UCT]: 2024-06-05 00:24:57 Age [y:d:h:m:s]: 00:317:06:20:41
Block: 1037225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226739 RingCT/type: yes/0
Extra: 012d47c8552f3576a8fcc05c1faf671c1d8613c76d4219e874b55a1cc80bfbc79402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af112bcdfe8a76d8bfb0400a899026d77eba19dec9c76b61f7e4e3b3de716dc1 0.600000000000 1505756 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": 1037235, "vin": [ { "gen": { "height": 1037225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af112bcdfe8a76d8bfb0400a899026d77eba19dec9c76b61f7e4e3b3de716dc1" } } ], "extra": [ 1, 45, 71, 200, 85, 47, 53, 118, 168, 252, 192, 92, 31, 175, 103, 28, 29, 134, 19, 199, 109, 66, 25, 232, 116, 181, 90, 28, 200, 11, 251, 199, 148, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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