Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb947d4c31db68ba3057bf4f60cf62d98613eae39dafeddb92b09f356f915aca

Tx prefix hash: 4dbe7eb310bc95ba545258108ea3c63c202063daa0769bf6798750e4b7e9c116
Tx public key: ef4c97c0612ba5cf0fd64b48bfe3b56c0e78aa38797308d72fff69e74d20c683
Timestamp: 1661268031 Timestamp [UCT]: 2022-08-23 15:20:31 Age [y:d:h:m:s]: 02:176:09:40:10
Block: 572168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647289 RingCT/type: yes/0
Extra: 01ef4c97c0612ba5cf0fd64b48bfe3b56c0e78aa38797308d72fff69e74d20c68302110000001fe6d27f9c000000000000000000

1 output(s) for total of 7.801354222000 dcy

stealth address amount amount idx
00: 746da2c1ba9326618d6d3155d3fbaf15f824621a3bc8f29a8c7ddd5765452fcf 7.801354222000 1005404 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": 572178, "vin": [ { "gen": { "height": 572168 } } ], "vout": [ { "amount": 7801354222, "target": { "key": "746da2c1ba9326618d6d3155d3fbaf15f824621a3bc8f29a8c7ddd5765452fcf" } } ], "extra": [ 1, 239, 76, 151, 192, 97, 43, 165, 207, 15, 214, 75, 72, 191, 227, 181, 108, 14, 120, 170, 56, 121, 115, 8, 215, 47, 255, 105, 231, 77, 32, 198, 131, 2, 17, 0, 0, 0, 31, 230, 210, 127, 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