Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec3d6823da87d14d1f3aef602a3fb28000e8b104034e3408dcef3ac208c3ab4

Tx prefix hash: e918044e0bd35cd62621c5bb1c7911fa262feb058539b99179b36aad282d6bed
Tx public key: 43ff6e651be4f8e761b11cc26cadd70e4adfba4579c1cf512acb211ad9ccc3ea
Timestamp: 1583932631 Timestamp [UCT]: 2020-03-11 13:17:11 Age [y:d:h:m:s]: 05:081:13:31:56
Block: 80488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214133 RingCT/type: yes/0
Extra: 0143ff6e651be4f8e761b11cc26cadd70e4adfba4579c1cf512acb211ad9ccc3ea02110000002fa08fd034000000000000000000

1 output(s) for total of 332.131932997000 dcy

stealth address amount amount idx
00: fdc10ec6c8dc35789e12fb2f34dddc7ab847b25ae40b1aa4720fd38890cb0856 332.131932997000 147292 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": 80498, "vin": [ { "gen": { "height": 80488 } } ], "vout": [ { "amount": 332131932997, "target": { "key": "fdc10ec6c8dc35789e12fb2f34dddc7ab847b25ae40b1aa4720fd38890cb0856" } } ], "extra": [ 1, 67, 255, 110, 101, 27, 228, 248, 231, 97, 177, 28, 194, 108, 173, 215, 14, 74, 223, 186, 69, 121, 193, 207, 81, 42, 203, 33, 26, 217, 204, 195, 234, 2, 17, 0, 0, 0, 47, 160, 143, 208, 52, 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