Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f635cdd7fc638640b03cd0953e4888a2d15ae4a4cd1a4a2fe057e872c0bcce

Tx prefix hash: 448452d4792eecddafd3a4f59bb4d9480cae6c9e9f54e0d9ea0c52d7be730367
Tx public key: 4766f33f879ec74dcbf7e9ba4c5ce97c509e853158103010eacd7c57b976ac1f
Timestamp: 1633161639 Timestamp [UCT]: 2021-10-02 08:00:39 Age [y:d:h:m:s]: 03:259:09:34:35
Block: 345040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 962064 RingCT/type: yes/0
Extra: 014766f33f879ec74dcbf7e9ba4c5ce97c509e853158103010eacd7c57b976ac1f021100000001f29d7abf000000000000000000

1 output(s) for total of 44.130583971000 dcy

stealth address amount amount idx
00: f6cfc4dd2ccfbaad50b7f5f42251acbc12ee87d75d3a0d4058d56ac0339e7d76 44.130583971000 707822 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": 345050, "vin": [ { "gen": { "height": 345040 } } ], "vout": [ { "amount": 44130583971, "target": { "key": "f6cfc4dd2ccfbaad50b7f5f42251acbc12ee87d75d3a0d4058d56ac0339e7d76" } } ], "extra": [ 1, 71, 102, 243, 63, 135, 158, 199, 77, 203, 247, 233, 186, 76, 92, 233, 124, 80, 158, 133, 49, 88, 16, 48, 16, 234, 205, 124, 87, 185, 118, 172, 31, 2, 17, 0, 0, 0, 1, 242, 157, 122, 191, 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