Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 480b5f646465556b6a989b66a4a01ea15ac2e7c60bcccfe7cf29d745a3f6121b

Tx prefix hash: 8cf5c2dd7e59d78cd54deecf81ccc7a840b40420aa8e3a649a78b6bbf3f6bd0c
Tx public key: cde2cc8f355f54bcf3d2e9170dc64ff6ff35907daf4849a2ef59272c20bb359a
Timestamp: 1710602065 Timestamp [UCT]: 2024-03-16 15:14:25 Age [y:d:h:m:s]: 00:257:04:59:59
Block: 979661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184117 RingCT/type: yes/0
Extra: 01cde2cc8f355f54bcf3d2e9170dc64ff6ff35907daf4849a2ef59272c20bb359a02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 402c6b2a7467c38335b5ff2ce4293ac6d19822bbc1d8097bb5718431bd025c8d 0.600000000000 1439712 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": 979671, "vin": [ { "gen": { "height": 979661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "402c6b2a7467c38335b5ff2ce4293ac6d19822bbc1d8097bb5718431bd025c8d" } } ], "extra": [ 1, 205, 226, 204, 143, 53, 95, 84, 188, 243, 210, 233, 23, 13, 198, 79, 246, 255, 53, 144, 125, 175, 72, 73, 162, 239, 89, 39, 44, 32, 187, 53, 154, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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