Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5fb6f728ee0d16218c7a3ae08a1f4d90b735ad83f5d686d75027410221c64c

Tx prefix hash: a7ae98cc0c98019aba97a9f5483ecc6f1ad52911a6e185b3beb585a4ce75b8db
Tx public key: 329be8b46e048a4642eeacff1078c393872fa869817a7847e6d06ebbca7cabd5
Timestamp: 1733327246 Timestamp [UCT]: 2024-12-04 15:47:26 Age [y:d:h:m:s]: 00:109:21:50:57
Block: 1167939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78353 RingCT/type: yes/0
Extra: 01329be8b46e048a4642eeacff1078c393872fa869817a7847e6d06ebbca7cabd5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7838043f589e195ae801a5af614e0d8c771111e24d99ec7f24104aacbf67f99d 0.600000000000 1653644 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": 1167949, "vin": [ { "gen": { "height": 1167939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7838043f589e195ae801a5af614e0d8c771111e24d99ec7f24104aacbf67f99d" } } ], "extra": [ 1, 50, 155, 232, 180, 110, 4, 138, 70, 66, 238, 172, 255, 16, 120, 195, 147, 135, 47, 168, 105, 129, 122, 120, 71, 230, 208, 110, 187, 202, 124, 171, 213, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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