Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d4450dcdd626db0a045a3ff5a4354a8e8c226603666a9c6e86e306e499b58c

Tx prefix hash: 57b5eeb3f850651d5715905255ad0121bfc5028188781f1d2eb6e0662eee73e5
Tx public key: 43ab04c817a6ca8f290a30d12655df307cc8d550d99bf4388912d501b47fcd10
Timestamp: 1729696727 Timestamp [UCT]: 2024-10-23 15:18:47 Age [y:d:h:m:s]: 00:186:23:33:07
Block: 1137919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133455 RingCT/type: yes/0
Extra: 0143ab04c817a6ca8f290a30d12655df307cc8d550d99bf4388912d501b47fcd100211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0073e891c87e1e3a4e8bbbdd91071f2fc6993638ddfd782e9399db32d7128de2 0.600000000000 1621504 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": 1137929, "vin": [ { "gen": { "height": 1137919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0073e891c87e1e3a4e8bbbdd91071f2fc6993638ddfd782e9399db32d7128de2" } } ], "extra": [ 1, 67, 171, 4, 200, 23, 166, 202, 143, 41, 10, 48, 209, 38, 85, 223, 48, 124, 200, 213, 80, 217, 155, 244, 56, 137, 18, 213, 1, 180, 127, 205, 16, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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