Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7133373d8f86b6142fb1b0c8ff3a76348602e98f77c905fad5de1128757d63d0

Tx prefix hash: ff436781cc041f94f195c2509744bfc43c5b391e01f46811219f7e7fe96e7574
Tx public key: 55dadcf89ab53f279262ff06e3d408818a2b831f4f0ea7c48e1f5ab108799c21
Timestamp: 1717961318 Timestamp [UCT]: 2024-06-09 19:28:38 Age [y:d:h:m:s]: 00:143:20:01:08
Block: 1040651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102951 RingCT/type: yes/0
Extra: 0155dadcf89ab53f279262ff06e3d408818a2b831f4f0ea7c48e1f5ab108799c210211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11f5fb32062cf4f848cfc49939b00a8a943727688715fa2af5db46c56df0d5c 0.600000000000 1509308 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": 1040661, "vin": [ { "gen": { "height": 1040651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11f5fb32062cf4f848cfc49939b00a8a943727688715fa2af5db46c56df0d5c" } } ], "extra": [ 1, 85, 218, 220, 248, 154, 181, 63, 39, 146, 98, 255, 6, 227, 212, 8, 129, 138, 43, 131, 31, 79, 14, 167, 196, 142, 31, 90, 177, 8, 121, 156, 33, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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