Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7169d49d7feb8cdbc4e437db470ce1364c37a76b5f149c6f4b3f15078c405a88

Tx prefix hash: c775b3490c11714f238e008c6ab23e84ef70bf1e2a7c54e571959ddb485e3d6e
Tx public key: f195fd0bcd8a1dbab68c75f93380dd7b6a28a5cc2c4b1abc2fcd356d55e5a850
Timestamp: 1722717101 Timestamp [UCT]: 2024-08-03 20:31:41 Age [y:d:h:m:s]: 00:245:13:09:13
Block: 1080075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175393 RingCT/type: yes/0
Extra: 01f195fd0bcd8a1dbab68c75f93380dd7b6a28a5cc2c4b1abc2fcd356d55e5a85002110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8b1fe3f5e75b7d718f1548e9df21af491089480c4d29b7e39c68c0a8bd6fe29 0.600000000000 1553298 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": 1080085, "vin": [ { "gen": { "height": 1080075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8b1fe3f5e75b7d718f1548e9df21af491089480c4d29b7e39c68c0a8bd6fe29" } } ], "extra": [ 1, 241, 149, 253, 11, 205, 138, 29, 186, 182, 140, 117, 249, 51, 128, 221, 123, 106, 40, 165, 204, 44, 75, 26, 188, 47, 205, 53, 109, 85, 229, 168, 80, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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