Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13a193777d6ca693e655284f6c0df7667bb254fe316d5db40bf5c6e1efa06e99

Tx prefix hash: cc17401b31fc0f59c4d1e4fa29da26bc47937913524051f8e0a7c150e2410a5a
Tx public key: 0922d730d5f06fb40d6abbe51da7850a9a4fcf53f50d1106ee756a5fa23b3bba
Timestamp: 1712904018 Timestamp [UCT]: 2024-04-12 06:40:18 Age [y:d:h:m:s]: 00:319:11:05:39
Block: 998704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228388 RingCT/type: yes/0
Extra: 010922d730d5f06fb40d6abbe51da7850a9a4fcf53f50d1106ee756a5fa23b3bba02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e522ad07d1c0fce4bd8eb2a46174b8b51cf763baf5cea36a98048ef0bb16ce8a 0.600000000000 1459156 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": 998714, "vin": [ { "gen": { "height": 998704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e522ad07d1c0fce4bd8eb2a46174b8b51cf763baf5cea36a98048ef0bb16ce8a" } } ], "extra": [ 1, 9, 34, 215, 48, 213, 240, 111, 180, 13, 106, 187, 229, 29, 167, 133, 10, 154, 79, 207, 83, 245, 13, 17, 6, 238, 117, 106, 95, 162, 59, 59, 186, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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