Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4198db8fe62cdf76f0221a40d9b4b26cbef7e2fcc0b41373595885be3bae79

Tx prefix hash: 1583c2bb34bc1872b13639a0c6811963022eec12639152d32629f73549dba051
Tx public key: bd7adb222e34ec8b652812bf82bc487f626868a75e4d81b5ae99f19dbf3d0122
Timestamp: 1726877144 Timestamp [UCT]: 2024-09-21 00:05:44 Age [y:d:h:m:s]: 00:055:03:02:02
Block: 1114569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39390 RingCT/type: yes/0
Extra: 01bd7adb222e34ec8b652812bf82bc487f626868a75e4d81b5ae99f19dbf3d012202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae694bf6b55bebc6edbfc45a241e28c68110c1b78e50e3b1e6b326f017fe396a 0.600000000000 1594396 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": 1114579, "vin": [ { "gen": { "height": 1114569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae694bf6b55bebc6edbfc45a241e28c68110c1b78e50e3b1e6b326f017fe396a" } } ], "extra": [ 1, 189, 122, 219, 34, 46, 52, 236, 139, 101, 40, 18, 191, 130, 188, 72, 127, 98, 104, 104, 167, 94, 77, 129, 181, 174, 153, 241, 157, 191, 61, 1, 34, 2, 17, 0, 0, 0, 6, 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