Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d45324a2576c3eb2ac2785c5a6444f503a7b345bde2d4fa73f61ab6520e4190

Tx prefix hash: 634977f35a03b63e901964f0d648b5aa3a22343a74e9692e74df5ef62577af7a
Tx public key: 20e6b61303f4f596c93a27ed4db43673b3ee1d783628cf13fa354dcb5767b9d9
Timestamp: 1735364957 Timestamp [UCT]: 2024-12-28 05:49:17 Age [y:d:h:m:s]: 00:090:09:52:59
Block: 1184806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64407 RingCT/type: yes/0
Extra: 0120e6b61303f4f596c93a27ed4db43673b3ee1d783628cf13fa354dcb5767b9d9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8906ecc1d494f967e727bacc64344cfc80092af124d120855e29e058679382a9 0.600000000000 1671265 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": 1184816, "vin": [ { "gen": { "height": 1184806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8906ecc1d494f967e727bacc64344cfc80092af124d120855e29e058679382a9" } } ], "extra": [ 1, 32, 230, 182, 19, 3, 244, 245, 150, 201, 58, 39, 237, 77, 180, 54, 115, 179, 238, 29, 120, 54, 40, 207, 19, 250, 53, 77, 203, 87, 103, 185, 217, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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