Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ce9eeb4a2fe121b72c1b788e951885c32a9b4b0195a859043eacfdbfbf9eac

Tx prefix hash: 11aa6730bd3d166d40eeb8fe4b24ed195e2564d6e4645bddb17b82e1098c5be1
Tx public key: 81ad46b9ba0fd00237969aecccc77c4d47ce1cafd03352b04e06334eab8fb396
Timestamp: 1725116030 Timestamp [UCT]: 2024-08-31 14:53:50 Age [y:d:h:m:s]: 00:218:01:57:23
Block: 1099966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155707 RingCT/type: yes/0
Extra: 0181ad46b9ba0fd00237969aecccc77c4d47ce1cafd03352b04e06334eab8fb396021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1339248c22890f2629feea0e33d394603a061c6acc94596399fde463b7f31a4e 0.600000000000 1575937 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": 1099976, "vin": [ { "gen": { "height": 1099966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1339248c22890f2629feea0e33d394603a061c6acc94596399fde463b7f31a4e" } } ], "extra": [ 1, 129, 173, 70, 185, 186, 15, 208, 2, 55, 150, 154, 236, 204, 199, 124, 77, 71, 206, 28, 175, 208, 51, 82, 176, 78, 6, 51, 78, 171, 143, 179, 150, 2, 17, 0, 0, 0, 7, 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