Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e234e7afc1f0f85a480bd1c9fd1168d46238ef6f094bb4893c53f4903bf40cd3

Tx prefix hash: bc0c222d466cb1bfb69ac134b751bae79ca0683d03e99ccb55d2a63a03ddd2e6
Tx public key: d7de6173daead39717457efb0a7638a106fb7281d3953d01f393e08be4362c2b
Timestamp: 1712340231 Timestamp [UCT]: 2024-04-05 18:03:51 Age [y:d:h:m:s]: 01:244:04:24:39
Block: 994016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433256 RingCT/type: yes/0
Extra: 01d7de6173daead39717457efb0a7638a106fb7281d3953d01f393e08be4362c2b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 281beb2a72ab056098fe56cb3b2dc49dfbc860e8d05ea66239e9082d69266769 0.600000000000 1454412 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": 994026, "vin": [ { "gen": { "height": 994016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "281beb2a72ab056098fe56cb3b2dc49dfbc860e8d05ea66239e9082d69266769" } } ], "extra": [ 1, 215, 222, 97, 115, 218, 234, 211, 151, 23, 69, 126, 251, 10, 118, 56, 161, 6, 251, 114, 129, 211, 149, 61, 1, 243, 147, 224, 139, 228, 54, 44, 43, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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