Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c0bfd2f136d91a07289be15aa6c42f2d0a9353394c8a6f6b79320ae1a06d6e

Tx prefix hash: d1fc87aa2d2015c19b99b2bbb87278912298fb0bc8f84f067b6ee0575f2898c0
Tx public key: 655e664035ef5a76740663daa7b5a4ce1baa8fae40a46c923f802a5337e15abb
Timestamp: 1661629875 Timestamp [UCT]: 2022-08-27 19:51:15 Age [y:d:h:m:s]: 02:282:20:39:04
Block: 575147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723472 RingCT/type: yes/0
Extra: 01655e664035ef5a76740663daa7b5a4ce1baa8fae40a46c923f802a5337e15abb02110000000275e3f0e9000000000000000000

1 output(s) for total of 7.626044401000 dcy

stealth address amount amount idx
00: bd8c4fb0d2c21bc638ec7586a4ae3ae3c4730c2a8930102c3afb470572b0877b 7.626044401000 1008481 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": 575157, "vin": [ { "gen": { "height": 575147 } } ], "vout": [ { "amount": 7626044401, "target": { "key": "bd8c4fb0d2c21bc638ec7586a4ae3ae3c4730c2a8930102c3afb470572b0877b" } } ], "extra": [ 1, 101, 94, 102, 64, 53, 239, 90, 118, 116, 6, 99, 218, 167, 181, 164, 206, 27, 170, 143, 174, 64, 164, 108, 146, 63, 128, 42, 83, 55, 225, 90, 187, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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