Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df33661f5c4587cf18ed58d4a5510f97246cce726ef4cfc0f435dfd2c2abfdc2

Tx prefix hash: 614b8abb46ed1da9011dc123e0745eccf1b3ba7754469872a1f78501722877e3
Tx public key: 1942e0bec9c4e5386ab177c1e356e8b2f9d81177e41ecc6d12e38a14b0316471
Timestamp: 1709581040 Timestamp [UCT]: 2024-03-04 19:37:20 Age [y:d:h:m:s]: 01:045:12:15:15
Block: 971184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293533 RingCT/type: yes/0
Extra: 011942e0bec9c4e5386ab177c1e356e8b2f9d81177e41ecc6d12e38a14b031647102110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d92bddc1503d4898d5e3a5d858e60891fae6cd7f919a7aae120fe3c8aacbe3dc 0.600000000000 1431069 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": 971194, "vin": [ { "gen": { "height": 971184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d92bddc1503d4898d5e3a5d858e60891fae6cd7f919a7aae120fe3c8aacbe3dc" } } ], "extra": [ 1, 25, 66, 224, 190, 201, 196, 229, 56, 106, 177, 119, 193, 227, 86, 232, 178, 249, 216, 17, 119, 228, 30, 204, 109, 18, 227, 138, 20, 176, 49, 100, 113, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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