Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241ce69c8871ccc09b3c38a4b7f61e0a1f22c1fe9776c6c2c9f35edb85e3a39d

Tx prefix hash: 862047c6ba77876c8ab752e00d908a5943d1f2939ad0b88c8472f6deff4f73c9
Tx public key: cf0f65d8e783234a225cb110cb2ff10a64b815940f89ce8d8265acbeced036d8
Timestamp: 1577160195 Timestamp [UCT]: 2019-12-24 04:03:15 Age [y:d:h:m:s]: 05:015:00:29:25
Block: 30331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160887 RingCT/type: yes/0
Extra: 01cf0f65d8e783234a225cb110cb2ff10a64b815940f89ce8d8265acbeced036d8021100000001d81c26c0000000000000000000

1 output(s) for total of 486.969395250000 dcy

stealth address amount amount idx
00: b7da6b8744ab1d021c48e08a81646d908521484c631dbe7be1faaecb278b20c3 486.969395250000 50083 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": 30341, "vin": [ { "gen": { "height": 30331 } } ], "vout": [ { "amount": 486969395250, "target": { "key": "b7da6b8744ab1d021c48e08a81646d908521484c631dbe7be1faaecb278b20c3" } } ], "extra": [ 1, 207, 15, 101, 216, 231, 131, 35, 74, 34, 92, 177, 16, 203, 47, 241, 10, 100, 184, 21, 148, 15, 137, 206, 141, 130, 101, 172, 190, 206, 208, 54, 216, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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