Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8fd1661316dfb084dee034506849b3c8f51849c32b3e816c51a878b84170cd2

Tx prefix hash: 4d58fdb4e7431619587d0d49a3f7d5fb17366ce3a5273aafcbbd03749c6bfb11
Tx public key: 4d063d2fc5af42e80162da9e2aec3c76eea7bdcd209f783849a630ac3cc9674e
Timestamp: 1734354806 Timestamp [UCT]: 2024-12-16 13:13:26 Age [y:d:h:m:s]: 00:183:08:05:46
Block: 1176478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130720 RingCT/type: yes/0
Extra: 014d063d2fc5af42e80162da9e2aec3c76eea7bdcd209f783849a630ac3cc9674e021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1346aced004fac0858399e17326095c485dbe9f1d06fbdcd8701a8f6b51c705 0.600000000000 1662811 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": 1176488, "vin": [ { "gen": { "height": 1176478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1346aced004fac0858399e17326095c485dbe9f1d06fbdcd8701a8f6b51c705" } } ], "extra": [ 1, 77, 6, 61, 47, 197, 175, 66, 232, 1, 98, 218, 158, 42, 236, 60, 118, 238, 167, 189, 205, 32, 159, 120, 56, 73, 166, 48, 172, 60, 201, 103, 78, 2, 17, 0, 0, 0, 5, 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