Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7c0d30f3d57368b65da314db72ccc423f6a1bbbd656b6dfaa388882f6a67e9

Tx prefix hash: d408cafe13798e2ae84907a5cbd171d30bfce20d9d20cc9e7e3e3d332085df60
Tx public key: 31d5880578a1d87b978d338027693546568f6b31d2cf0ee424c94f126506b4ba
Timestamp: 1699741627 Timestamp [UCT]: 2023-11-11 22:27:07 Age [y:d:h:m:s]: 01:104:11:01:32
Block: 889609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335795 RingCT/type: yes/0
Extra: 0131d5880578a1d87b978d338027693546568f6b31d2cf0ee424c94f126506b4ba021100000003faf35c9c000000000000000000

1 output(s) for total of 0.692398451000 dcy

stealth address amount amount idx
00: 6af0ca5f5ca499812175da374039a3efa4642970526c48d2a36a37e722f42af5 0.692398451000 1345614 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": 889619, "vin": [ { "gen": { "height": 889609 } } ], "vout": [ { "amount": 692398451, "target": { "key": "6af0ca5f5ca499812175da374039a3efa4642970526c48d2a36a37e722f42af5" } } ], "extra": [ 1, 49, 213, 136, 5, 120, 161, 216, 123, 151, 141, 51, 128, 39, 105, 53, 70, 86, 143, 107, 49, 210, 207, 14, 228, 36, 201, 79, 18, 101, 6, 180, 186, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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