Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724c527b5bbe6be65f6c3330d847ada8e30df0c9de038ef59917efd6151e210c

Tx prefix hash: 4ce492a2ccb67bfbfe3a06b701f32cbe7a61bd1d03b2521958d8d033392483d5
Tx public key: d30fcf8c1a0ad9c8af0be8b635a7777914996d7694e8679029315a7ecca04175
Timestamp: 1701258247 Timestamp [UCT]: 2023-11-29 11:44:07 Age [y:d:h:m:s]: 01:157:23:57:12
Block: 902179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374094 RingCT/type: yes/0
Extra: 01d30fcf8c1a0ad9c8af0be8b635a7777914996d7694e8679029315a7ecca041750211000000014b8f5122000000000000000000

1 output(s) for total of 0.629080815000 dcy

stealth address amount amount idx
00: d76fb064fd514d0f5f87675a116f03d3a75b510326d377afe76dcbede48bf701 0.629080815000 1358796 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": 902189, "vin": [ { "gen": { "height": 902179 } } ], "vout": [ { "amount": 629080815, "target": { "key": "d76fb064fd514d0f5f87675a116f03d3a75b510326d377afe76dcbede48bf701" } } ], "extra": [ 1, 211, 15, 207, 140, 26, 10, 217, 200, 175, 11, 232, 182, 53, 167, 119, 121, 20, 153, 109, 118, 148, 232, 103, 144, 41, 49, 90, 126, 204, 160, 65, 117, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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