Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae144b4f566c0d43abf84947d5ebe4ef0f1c2dd1e5cc4853dca367ad6bd62af

Tx prefix hash: e2c39474259af429b92ec59dede4bd3d1484419e4f6649618854aca22a1c0c62
Tx public key: 15a87dfcab422b092e39ae3e05465ed211e52099656357ff4063a78b3d2a2f98
Timestamp: 1712897125 Timestamp [UCT]: 2024-04-12 04:45:25 Age [y:d:h:m:s]: 01:065:19:25:32
Block: 998643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307939 RingCT/type: yes/0
Extra: 0115a87dfcab422b092e39ae3e05465ed211e52099656357ff4063a78b3d2a2f980211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2843c971d8b20a4f098717f5286cc7f3fe3adb8eb45893995c2e2b3374ce1a0 0.600000000000 1459095 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": 998653, "vin": [ { "gen": { "height": 998643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2843c971d8b20a4f098717f5286cc7f3fe3adb8eb45893995c2e2b3374ce1a0" } } ], "extra": [ 1, 21, 168, 125, 252, 171, 66, 43, 9, 46, 57, 174, 62, 5, 70, 94, 210, 17, 229, 32, 153, 101, 99, 87, 255, 64, 99, 167, 139, 61, 42, 47, 152, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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