Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b31b80da40ebdd41b614da640f1b8407de253f43dd49a160ee26e4de3460bde

Tx prefix hash: 0f846fb6e99e38f75524e4e207db95789d6426f4a3499b4e65c9f147685f1b45
Tx public key: be9ee41e61a90d07abd505eaadb14baa412f100758b76d798aaa84a31ea3a46b
Timestamp: 1722098488 Timestamp [UCT]: 2024-07-27 16:41:28 Age [y:d:h:m:s]: 00:250:09:01:31
Block: 1074953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178841 RingCT/type: yes/0
Extra: 01be9ee41e61a90d07abd505eaadb14baa412f100758b76d798aaa84a31ea3a46b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 678bd93d08c49f0fc1154991081d17e2aedcbd5386d23a7f1df71f0bcb2c3ced 0.600000000000 1547472 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": 1074963, "vin": [ { "gen": { "height": 1074953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "678bd93d08c49f0fc1154991081d17e2aedcbd5386d23a7f1df71f0bcb2c3ced" } } ], "extra": [ 1, 190, 158, 228, 30, 97, 169, 13, 7, 171, 213, 5, 234, 173, 177, 75, 170, 65, 47, 16, 7, 88, 183, 109, 121, 138, 170, 132, 163, 30, 163, 164, 107, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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