Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9d93cf4bfe6fc549f07209c0e97b9b96d399593f54d4e4a7370941e854d694

Tx prefix hash: d6b53b3ef136f79779889b169e8157a2be3f141353d13d3db85a567dbf3a84be
Tx public key: 19baa6b1f7844a7de60c7ada4ce5aab38e5f1adf17f09e1fc71f9ed878406d65
Timestamp: 1725592904 Timestamp [UCT]: 2024-09-06 03:21:44 Age [y:d:h:m:s]: 00:079:15:55:41
Block: 1103922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56968 RingCT/type: yes/0
Extra: 0119baa6b1f7844a7de60c7ada4ce5aab38e5f1adf17f09e1fc71f9ed878406d6502110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74945bcc6a0daff22f8ab3d03028d0d74a42639649044a4444d5f3a94596d36a 0.600000000000 1580937 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": 1103932, "vin": [ { "gen": { "height": 1103922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74945bcc6a0daff22f8ab3d03028d0d74a42639649044a4444d5f3a94596d36a" } } ], "extra": [ 1, 25, 186, 166, 177, 247, 132, 74, 125, 230, 12, 122, 218, 76, 229, 170, 179, 142, 95, 26, 223, 23, 240, 158, 31, 199, 31, 158, 216, 120, 64, 109, 101, 2, 17, 0, 0, 0, 15, 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