Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ff48ee174a5302986a687cb8b948fef5286526e84290e2f7fb3b729c5d14b2

Tx prefix hash: 8defca8350134cdd98b0069188759552edf1c7e976b0acaa175bb715a3c06fa9
Tx public key: 1e0754f5d1e5c064070328c4a580ad66fcf03861dde32beb592323fa48c0c504
Timestamp: 1719902640 Timestamp [UCT]: 2024-07-02 06:44:00 Age [y:d:h:m:s]: 00:289:18:07:25
Block: 1056749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207030 RingCT/type: yes/0
Extra: 011e0754f5d1e5c064070328c4a580ad66fcf03861dde32beb592323fa48c0c50402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ab1d72bdf42dd01ab96f58b7992d74106a56b6c3fb4decf6d0ace2537d43a2 0.600000000000 1527170 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": 1056759, "vin": [ { "gen": { "height": 1056749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ab1d72bdf42dd01ab96f58b7992d74106a56b6c3fb4decf6d0ace2537d43a2" } } ], "extra": [ 1, 30, 7, 84, 245, 209, 229, 192, 100, 7, 3, 40, 196, 165, 128, 173, 102, 252, 240, 56, 97, 221, 227, 43, 235, 89, 35, 35, 250, 72, 192, 197, 4, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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