Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36f60c94d7ded364d0b9080380fba2c64706e44aa26f4dd2ee5c1551eb75533

Tx prefix hash: 86b35a4f2d61df83249feec4cae95c8e2e328b4351b6db6fc29437e9ba465b48
Tx public key: 816bdf5d95ebd55def37a8e6d43ec64ce5640c733f178cfe76f0d1ac3cc64d86
Timestamp: 1696766383 Timestamp [UCT]: 2023-10-08 11:59:43 Age [y:d:h:m:s]: 01:219:07:44:43
Block: 865143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417819 RingCT/type: yes/0
Extra: 01816bdf5d95ebd55def37a8e6d43ec64ce5640c733f178cfe76f0d1ac3cc64d86021100000004bfa22221000000000000000000

1 output(s) for total of 0.834491923000 dcy

stealth address amount amount idx
00: 06da9a754974ad399331b7c449fbbeaf8347467383470bd992d053d15261a37d 0.834491923000 1319669 of 0

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": 865153, "vin": [ { "gen": { "height": 865143 } } ], "vout": [ { "amount": 834491923, "target": { "key": "06da9a754974ad399331b7c449fbbeaf8347467383470bd992d053d15261a37d" } } ], "extra": [ 1, 129, 107, 223, 93, 149, 235, 213, 93, 239, 55, 168, 230, 212, 62, 198, 76, 229, 100, 12, 115, 63, 23, 140, 254, 118, 240, 209, 172, 60, 198, 77, 134, 2, 17, 0, 0, 0, 4, 191, 162, 34, 33, 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