Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce897814b75cfb5d6f7feeeae6ad5ac37be94cbef7cdc57b29025b593806345

Tx prefix hash: 418b765e7a3aa10cf37dce407cc3733e8055b26c7a36e039966fb44845e83c4b
Tx public key: 112c5b435becd63b347c1e40fd7af98c11e66cfb7a33135415cebc34e88cd39f
Timestamp: 1720678421 Timestamp [UCT]: 2024-07-11 06:13:41 Age [y:d:h:m:s]: 01:123:15:02:41
Block: 1063188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346867 RingCT/type: yes/0
Extra: 01112c5b435becd63b347c1e40fd7af98c11e66cfb7a33135415cebc34e88cd39f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9ad810ef3b7c74385fe26f1d5c8d94c482cddf11d20bc3ae26e4b12e38db34d 0.600000000000 1533703 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": 1063198, "vin": [ { "gen": { "height": 1063188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ad810ef3b7c74385fe26f1d5c8d94c482cddf11d20bc3ae26e4b12e38db34d" } } ], "extra": [ 1, 17, 44, 91, 67, 91, 236, 214, 59, 52, 124, 30, 64, 253, 122, 249, 140, 17, 230, 108, 251, 122, 51, 19, 84, 21, 206, 188, 52, 232, 140, 211, 159, 2, 17, 0, 0, 0, 6, 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