Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd3cd35303b7368c18f9c409d6808c5ad1ae14a425ed90278821711221601ce

Tx prefix hash: b39637f259d1d5cd38d22b1034fa2feb60fbfb11df65090a7fdb6817942b3e98
Tx public key: 6d2ad564256aaa1fe02bf4b9fd9c395bb570c243d1f9e69d596ce921bb2f69db
Timestamp: 1673102474 Timestamp [UCT]: 2023-01-07 14:41:14 Age [y:d:h:m:s]: 02:098:20:48:14
Block: 669609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592347 RingCT/type: yes/0
Extra: 016d2ad564256aaa1fe02bf4b9fd9c395bb570c243d1f9e69d596ce921bb2f69db02110000000352542ceb000000000000000000

1 output(s) for total of 3.709431648000 dcy

stealth address amount amount idx
00: 2afb65b4013134d8b1c9326498dc8bef5a4205bf2b26e541d261789b99ac921d 3.709431648000 1110954 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": 669619, "vin": [ { "gen": { "height": 669609 } } ], "vout": [ { "amount": 3709431648, "target": { "key": "2afb65b4013134d8b1c9326498dc8bef5a4205bf2b26e541d261789b99ac921d" } } ], "extra": [ 1, 109, 42, 213, 100, 37, 106, 170, 31, 224, 43, 244, 185, 253, 156, 57, 91, 181, 112, 194, 67, 209, 249, 230, 157, 89, 108, 233, 33, 187, 47, 105, 219, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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