Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faf009b60ffb19b1cecc73ab74682916aa9cf8d3789634a99046c489fca3a7a4

Tx prefix hash: f4f758837475f81d0928ebbf6d8e3d34b6fc262fce0700a409718d390f83a253
Tx public key: 087bec62ae06d7463930ba4059a39ae3b0470e93ab93021e86beafe5c9986a61
Timestamp: 1726526034 Timestamp [UCT]: 2024-09-16 22:33:54 Age [y:d:h:m:s]: 01:052:09:23:46
Block: 1111656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295859 RingCT/type: yes/0
Extra: 01087bec62ae06d7463930ba4059a39ae3b0470e93ab93021e86beafe5c9986a61021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8db2ca5aabec729ed0e815f860227e8bfb1a2372fdf86ee8ed1cefda4efe9b5 0.600000000000 1590693 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": 1111666, "vin": [ { "gen": { "height": 1111656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8db2ca5aabec729ed0e815f860227e8bfb1a2372fdf86ee8ed1cefda4efe9b5" } } ], "extra": [ 1, 8, 123, 236, 98, 174, 6, 215, 70, 57, 48, 186, 64, 89, 163, 154, 227, 176, 71, 14, 147, 171, 147, 2, 30, 134, 190, 175, 229, 201, 152, 106, 97, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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