Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ecab9d9621bc235255e34d8c39b13d8590f8c784d3bd5deb0e4b5088c59bf3a

Tx prefix hash: 7edd215cd28c154920ead9c722e33a0b3dcb5e543f0ff6509724065859f98c27
Tx public key: 42549ff8c8f5381268b0aa8f3fc8ab2d307fe1c957050678b0751fa7f8c9d0b9
Timestamp: 1580374821 Timestamp [UCT]: 2020-01-30 09:00:21 Age [y:d:h:m:s]: 04:330:23:15:47
Block: 55162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127591 RingCT/type: yes/0
Extra: 0142549ff8c8f5381268b0aa8f3fc8ab2d307fe1c957050678b0751fa7f8c9d0b9021100000004b221b3d1000000000000000000

1 output(s) for total of 402.926861109000 dcy

stealth address amount amount idx
00: 99bc6e1b2a13f94b6d54f1d24e74794e8e1fb551e90cd4f3db860acefb99a8da 402.926861109000 101913 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": 55172, "vin": [ { "gen": { "height": 55162 } } ], "vout": [ { "amount": 402926861109, "target": { "key": "99bc6e1b2a13f94b6d54f1d24e74794e8e1fb551e90cd4f3db860acefb99a8da" } } ], "extra": [ 1, 66, 84, 159, 248, 200, 245, 56, 18, 104, 176, 170, 143, 63, 200, 171, 45, 48, 127, 225, 201, 87, 5, 6, 120, 176, 117, 31, 167, 248, 201, 208, 185, 2, 17, 0, 0, 0, 4, 178, 33, 179, 209, 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