Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 626212a39f665c633238a4a4afde290f3d58b93a69fb1959f2f8eee28abb5a30

Tx prefix hash: 1bdfef84bb3bcb44cdd55bb1e477b391cf05350a265a0e9f1b1c4596138dcae4
Tx public key: d2dd0862d57d5faff296ae7d894f2de4fedd434d15c8be54c22d2a95924a0c59
Timestamp: 1722696180 Timestamp [UCT]: 2024-08-03 14:43:00 Age [y:d:h:m:s]: 00:237:18:48:03
Block: 1079901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169843 RingCT/type: yes/0
Extra: 01d2dd0862d57d5faff296ae7d894f2de4fedd434d15c8be54c22d2a95924a0c59021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ae65693a47eea72db973e37397fdecd0a2900d0202aa4bb22c66393e256fee 0.600000000000 1553054 of 15

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": 1079911, "vin": [ { "gen": { "height": 1079901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ae65693a47eea72db973e37397fdecd0a2900d0202aa4bb22c66393e256fee" } } ], "extra": [ 1, 210, 221, 8, 98, 213, 125, 95, 175, 242, 150, 174, 125, 137, 79, 45, 228, 254, 221, 67, 77, 21, 200, 190, 84, 194, 45, 42, 149, 146, 74, 12, 89, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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