Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977c60aca5dc3bb25d8014c31b1f9ea577c5bad6447037419ac6c5c26e12016a

Tx prefix hash: 6441474a2fc5eadfd4ae9bb16164ab8dbbf965d2cb0047a6fcac16b6a16a017a
Tx public key: 8d27a11bc13632aa9a73a82af41dbdb7e0355b01fb7d5b991d72c2d5dc1e6a9e
Timestamp: 1734651493 Timestamp [UCT]: 2024-12-19 23:38:13 Age [y:d:h:m:s]: 00:329:15:29:01
Block: 1178937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233084 RingCT/type: yes/0
Extra: 018d27a11bc13632aa9a73a82af41dbdb7e0355b01fb7d5b991d72c2d5dc1e6a9e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ca5917f99ada5ead3f17f4faf5fe641636d94106365fd7f90a0e5493ea515d2 0.600000000000 1665328 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": 1178947, "vin": [ { "gen": { "height": 1178937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ca5917f99ada5ead3f17f4faf5fe641636d94106365fd7f90a0e5493ea515d2" } } ], "extra": [ 1, 141, 39, 161, 27, 193, 54, 50, 170, 154, 115, 168, 42, 244, 29, 189, 183, 224, 53, 91, 1, 251, 125, 91, 153, 29, 114, 194, 213, 220, 30, 106, 158, 2, 17, 0, 0, 0, 2, 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