Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef48bd412ab3de808349e4e104f7b17fe2f6ed089430c6aff5abeebea24431f

Tx prefix hash: c84085a8143db7d2c323b86c93deaab6108bfdcbad68e7b9ce8c1f8db85015bf
Tx public key: 12bf8ef6b6f692946e8faa0d95fdf73d448c5eb648e8aef69b8ae8c977bc17e4
Timestamp: 1703070913 Timestamp [UCT]: 2023-12-20 11:15:13 Age [y:d:h:m:s]: 01:111:18:48:53
Block: 917209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341015 RingCT/type: yes/0
Extra: 0112bf8ef6b6f692946e8faa0d95fdf73d448c5eb648e8aef69b8ae8c977bc17e4021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b264043f8f7908ac5373654295b3b01a14f6fdb6d27f0502cfbc2fbf675f0b4 0.600000000000 1374779 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": 917219, "vin": [ { "gen": { "height": 917209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b264043f8f7908ac5373654295b3b01a14f6fdb6d27f0502cfbc2fbf675f0b4" } } ], "extra": [ 1, 18, 191, 142, 246, 182, 246, 146, 148, 110, 143, 170, 13, 149, 253, 247, 61, 68, 140, 94, 182, 72, 232, 174, 246, 155, 138, 232, 201, 119, 188, 23, 228, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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