Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b713f21ddc0ca48a432ad161eedc7a2711cf7a81248f19d690796de5e599c112

Tx prefix hash: e594b58e163578c8ebc1481f36f4356b4b827e79e06bcdcacff4730c77c9e217
Tx public key: f21f0583ea5a5ead4a790da96cb3aa81640f51f347a32ef6455fa4d3498c5539
Timestamp: 1730874588 Timestamp [UCT]: 2024-11-06 06:29:48 Age [y:d:h:m:s]: 00:018:09:14:20
Block: 1147614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13179 RingCT/type: yes/0
Extra: 01f21f0583ea5a5ead4a790da96cb3aa81640f51f347a32ef6455fa4d3498c5539021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737a9dd386491e13fc8e72273d9baf6ccf948a4f5f1641676298a79c90c5a3d3 0.600000000000 1632313 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": 1147624, "vin": [ { "gen": { "height": 1147614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737a9dd386491e13fc8e72273d9baf6ccf948a4f5f1641676298a79c90c5a3d3" } } ], "extra": [ 1, 242, 31, 5, 131, 234, 90, 94, 173, 74, 121, 13, 169, 108, 179, 170, 129, 100, 15, 81, 243, 71, 163, 46, 246, 69, 95, 164, 211, 73, 140, 85, 57, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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