Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 460d5567d995ae92ea7b2fa2b89efcca1bbfa086f3ead604a924707816177753

Tx prefix hash: 41c740bbb1259cd264e2d8356a34a4ec3aae5fd99b0971e6a302782bc4f86dd1
Tx public key: e61cf672f89aa6fab5e8f078b22f12007516a69dd58df6cb5d38643bbe74f6d8
Timestamp: 1702069848 Timestamp [UCT]: 2023-12-08 21:10:48 Age [y:d:h:m:s]: 01:339:12:01:26
Block: 908904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501506 RingCT/type: yes/0
Extra: 01e61cf672f89aa6fab5e8f078b22f12007516a69dd58df6cb5d38643bbe74f6d802110000000133af99f4000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 34b7677bae8a274a9233775258f72619f10fd3cd60a3d7782e866a101fa1ded5 0.600010000000 1365963 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": 908914, "vin": [ { "gen": { "height": 908904 } } ], "vout": [ { "amount": 600010000, "target": { "key": "34b7677bae8a274a9233775258f72619f10fd3cd60a3d7782e866a101fa1ded5" } } ], "extra": [ 1, 230, 28, 246, 114, 248, 154, 166, 250, 181, 232, 240, 120, 178, 47, 18, 0, 117, 22, 166, 157, 213, 141, 246, 203, 93, 56, 100, 59, 190, 116, 246, 216, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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