Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de697fc379415489a49fefac62d56e82089b6b1f1eb417d56d498d530fd3fb30

Tx prefix hash: 8ac55cc96d25c7b9375a85355fbb0e448ea408ec41a630684e6efb8180a0ee5e
Tx public key: 56cfbdf32408d805d4ae9393ca662f83e08d404b4647f1dd0c1d56ec4f5a32df
Timestamp: 1673840980 Timestamp [UCT]: 2023-01-16 03:49:40 Age [y:d:h:m:s]: 02:312:21:40:51
Block: 675734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 743040 RingCT/type: yes/0
Extra: 0156cfbdf32408d805d4ae9393ca662f83e08d404b4647f1dd0c1d56ec4f5a32df0211000000048b7b6602000000000000000000

1 output(s) for total of 3.540076901000 dcy

stealth address amount amount idx
00: add72625397971f5f1370f16bd0109e8bbef5ba432e7fdca069f5b332fcbedbc 3.540076901000 1117417 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": 675744, "vin": [ { "gen": { "height": 675734 } } ], "vout": [ { "amount": 3540076901, "target": { "key": "add72625397971f5f1370f16bd0109e8bbef5ba432e7fdca069f5b332fcbedbc" } } ], "extra": [ 1, 86, 207, 189, 243, 36, 8, 216, 5, 212, 174, 147, 147, 202, 102, 47, 131, 224, 141, 64, 75, 70, 71, 241, 221, 12, 29, 86, 236, 79, 90, 50, 223, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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