Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b133298a8da2c13eab2929bd6b43d7fdb7b9473353cf4404b5061305c7f1c0ab

Tx prefix hash: 15f8695cebd3f56893b15bd49d3fca9043cbda79cb8d58465084a0a79633aaf6
Tx public key: d3aad2060a045aef4e6b90726693c77ee9c8dc7be21634fc9b798e16afb61e19
Timestamp: 1703068437 Timestamp [UCT]: 2023-12-20 10:33:57 Age [y:d:h:m:s]: 01:174:10:14:12
Block: 917186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385812 RingCT/type: yes/0
Extra: 01d3aad2060a045aef4e6b90726693c77ee9c8dc7be21634fc9b798e16afb61e190211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aef0f2c1e61d06d87b33baa1071f722f7640901e4129db91f4f85309d5c9fb7 0.600000000000 1374756 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": 917196, "vin": [ { "gen": { "height": 917186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aef0f2c1e61d06d87b33baa1071f722f7640901e4129db91f4f85309d5c9fb7" } } ], "extra": [ 1, 211, 170, 210, 6, 10, 4, 90, 239, 78, 107, 144, 114, 102, 147, 199, 126, 233, 200, 220, 123, 226, 22, 52, 252, 155, 121, 142, 22, 175, 182, 30, 25, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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