Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 289ff6ed1bc3b10b7df170e0f002ec6e2074ed27377f08f616c26238dcc58b05

Tx prefix hash: 35dff639e29d7a2569f8e35b3a3e039b7273e3f74db729dd9e0fe140cd46546d
Tx public key: b66672d3701648eddcb9fccdd2c9f87f0c239cdaf21e294db2dbd6b3e5a5da64
Timestamp: 1680078124 Timestamp [UCT]: 2023-03-29 08:22:04 Age [y:d:h:m:s]: 02:009:20:11:14
Block: 727482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528539 RingCT/type: yes/0
Extra: 01b66672d3701648eddcb9fccdd2c9f87f0c239cdaf21e294db2dbd6b3e5a5da6402110000000183600029000000000000000000

1 output(s) for total of 2.385340478000 dcy

stealth address amount amount idx
00: d3264b400e4954c7489c1427f7a5857742c9231d021225be130f5758797d8ee7 2.385340478000 1172787 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": 727492, "vin": [ { "gen": { "height": 727482 } } ], "vout": [ { "amount": 2385340478, "target": { "key": "d3264b400e4954c7489c1427f7a5857742c9231d021225be130f5758797d8ee7" } } ], "extra": [ 1, 182, 102, 114, 211, 112, 22, 72, 237, 220, 185, 252, 205, 210, 201, 248, 127, 12, 35, 156, 218, 242, 30, 41, 77, 178, 219, 214, 179, 229, 165, 218, 100, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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