Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ebf376012cbb097f0c5344bfaada5a4d916829ed7ac35c3ee5f8eb15749842

Tx prefix hash: 371ba7bed6ab76a7c0ebd6f06de7c2d04c1ccd233a903a5d49773e8de2311a7e
Tx public key: 708ab6318e7793c3b8e65debd9098ddcba3799015b22e8e4892ce8e0719ad406
Timestamp: 1725479445 Timestamp [UCT]: 2024-09-04 19:50:45 Age [y:d:h:m:s]: 00:080:23:08:51
Block: 1102985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57891 RingCT/type: yes/0
Extra: 01708ab6318e7793c3b8e65debd9098ddcba3799015b22e8e4892ce8e0719ad40602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a85dd6d33d4b65fa7b8e28fbebc8462865eb68fdb8e1be5bb80bdf0f9b98d0e5 0.600000000000 1579638 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": 1102995, "vin": [ { "gen": { "height": 1102985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a85dd6d33d4b65fa7b8e28fbebc8462865eb68fdb8e1be5bb80bdf0f9b98d0e5" } } ], "extra": [ 1, 112, 138, 182, 49, 142, 119, 147, 195, 184, 230, 93, 235, 217, 9, 141, 220, 186, 55, 153, 1, 91, 34, 232, 228, 137, 44, 232, 224, 113, 154, 212, 6, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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