Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e88fc83cc6d79c56d926ba95d874b24b78fa4c7b3b20514c12120976230b23f

Tx prefix hash: 70880208391259bf434416bab6b7a01f20f873c3e142e7737839513f567ee3a9
Tx public key: 91e8ae01cb14d648998785a0a8e91cfc8531c8f3d603eeeea129cb0555a18c5e
Timestamp: 1700602352 Timestamp [UCT]: 2023-11-21 21:32:32 Age [y:d:h:m:s]: 01:135:07:28:06
Block: 896734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357875 RingCT/type: yes/0
Extra: 0191e8ae01cb14d648998785a0a8e91cfc8531c8f3d603eeeea129cb0555a18c5e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.655764639000 dcy

stealth address amount amount idx
00: f039995b518d8a46f5790c208e93ea2fb6cf3b9f508a8c8ec6c7f59e4ffd503c 0.655764639000 1353075 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": 896744, "vin": [ { "gen": { "height": 896734 } } ], "vout": [ { "amount": 655764639, "target": { "key": "f039995b518d8a46f5790c208e93ea2fb6cf3b9f508a8c8ec6c7f59e4ffd503c" } } ], "extra": [ 1, 145, 232, 174, 1, 203, 20, 214, 72, 153, 135, 133, 160, 168, 233, 28, 252, 133, 49, 200, 243, 214, 3, 238, 238, 161, 41, 203, 5, 85, 161, 140, 94, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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