Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df70c9c33e763c247a2f135d8d63a22a21302ccbcba676ea513573c4743af212

Tx prefix hash: b5eeaec78e94a8c64edf49285ffcc58f1ecbdd7cded4f454558bdb0e37a75834
Tx public key: cbf5a20b97bd6f32f96afa04f24c55048d49b2aaa1952bc28e7192765ba95c9d
Timestamp: 1577763266 Timestamp [UCT]: 2019-12-31 03:34:26 Age [y:d:h:m:s]: 05:065:10:43:49
Block: 35447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196560 RingCT/type: yes/0
Extra: 01cbf5a20b97bd6f32f96afa04f24c55048d49b2aaa1952bc28e7192765ba95c9d0211000000218a2ee0d9000000000000000000

1 output(s) for total of 468.328112973000 dcy

stealth address amount amount idx
00: 72f6fcc32e82de7a7b0c3c7bfcf1f6eb0946d1ebc04115579cffaa353d211906 468.328112973000 59781 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": 35457, "vin": [ { "gen": { "height": 35447 } } ], "vout": [ { "amount": 468328112973, "target": { "key": "72f6fcc32e82de7a7b0c3c7bfcf1f6eb0946d1ebc04115579cffaa353d211906" } } ], "extra": [ 1, 203, 245, 162, 11, 151, 189, 111, 50, 249, 106, 250, 4, 242, 76, 85, 4, 141, 73, 178, 170, 161, 149, 43, 194, 142, 113, 146, 118, 91, 169, 92, 157, 2, 17, 0, 0, 0, 33, 138, 46, 224, 217, 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