Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05edb509af9c7c12e636783243c82bb6f54cbb45ab3c3337ef9523f3251d488d

Tx prefix hash: b2408b6c1ece4a8a6d1f36c02f79f86a9ac82aa677d16951b410daa435e59857
Tx public key: c32f75bba0a84bf0447485f433263ebea54a2d57396dc909c3a9cf897caa1dea
Timestamp: 1679498290 Timestamp [UCT]: 2023-03-22 15:18:10 Age [y:d:h:m:s]: 02:052:15:12:29
Block: 722676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559159 RingCT/type: yes/0
Extra: 01c32f75bba0a84bf0447485f433263ebea54a2d57396dc909c3a9cf897caa1dea021100000003faf35c9c000000000000000000

1 output(s) for total of 2.474425001000 dcy

stealth address amount amount idx
00: d26270434e07149bffc87aea03e2c191e8542a4c6875fb2f96fd028237e266d1 2.474425001000 1167623 of 0

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": 722686, "vin": [ { "gen": { "height": 722676 } } ], "vout": [ { "amount": 2474425001, "target": { "key": "d26270434e07149bffc87aea03e2c191e8542a4c6875fb2f96fd028237e266d1" } } ], "extra": [ 1, 195, 47, 117, 187, 160, 168, 75, 240, 68, 116, 133, 244, 51, 38, 62, 190, 165, 74, 45, 87, 57, 109, 201, 9, 195, 169, 207, 137, 124, 170, 29, 234, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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