Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 127ff356bd96d3a75a25a42c07ef7ab3797b6a5a18f5967f51452b0f49acc796

Tx prefix hash: e2589ea9936ef87eb4d679744198f8a201269d93c13755b9549f419d501cb35e
Tx public key: fb95480743ab9dcb9be3f83e419f929faa26fd2f33735f9c8bb5e74f62de61c6
Timestamp: 1634352203 Timestamp [UCT]: 2021-10-16 02:43:23 Age [y:d:h:m:s]: 03:117:21:43:39
Block: 353965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 861893 RingCT/type: yes/0
Extra: 01fb95480743ab9dcb9be3f83e419f929faa26fd2f33735f9c8bb5e74f62de61c602110000000a8d0de867000000000000000000

1 output(s) for total of 41.225642698000 dcy

stealth address amount amount idx
00: 6cd1e3a317941e2dc53dc35b04d620e58f556fa9d8124b5d749b0f6f3c60fe61 41.225642698000 723153 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": 353975, "vin": [ { "gen": { "height": 353965 } } ], "vout": [ { "amount": 41225642698, "target": { "key": "6cd1e3a317941e2dc53dc35b04d620e58f556fa9d8124b5d749b0f6f3c60fe61" } } ], "extra": [ 1, 251, 149, 72, 7, 67, 171, 157, 203, 155, 227, 248, 62, 65, 159, 146, 159, 170, 38, 253, 47, 51, 115, 95, 156, 139, 181, 231, 79, 98, 222, 97, 198, 2, 17, 0, 0, 0, 10, 141, 13, 232, 103, 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