Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824e12657c6741c5a2803023c51cfddaf2c52bd23de2eef93fdfccbdc9fcf8d0

Tx prefix hash: 734b82a9df27a7f57f926c0f97ec90adf2d2fbb7810b7681a0d255d589c38468
Tx public key: d32116c6f8ad0c6b250c3da802da381419554be8a3fb65d0fe7bbb365ca3f9b5
Timestamp: 1662264342 Timestamp [UCT]: 2022-09-04 04:05:42 Age [y:d:h:m:s]: 03:058:16:43:11
Block: 580379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 821798 RingCT/type: yes/0
Extra: 01d32116c6f8ad0c6b250c3da802da381419554be8a3fb65d0fe7bbb365ca3f9b502110000001475e3f0e9000000000000000000

1 output(s) for total of 7.327630033000 dcy

stealth address amount amount idx
00: e6298b5b10ad382095c653f8aeebc955ac7088b1f184ac7b049a25ba90d2d05a 7.327630033000 1013905 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": 580389, "vin": [ { "gen": { "height": 580379 } } ], "vout": [ { "amount": 7327630033, "target": { "key": "e6298b5b10ad382095c653f8aeebc955ac7088b1f184ac7b049a25ba90d2d05a" } } ], "extra": [ 1, 211, 33, 22, 198, 248, 173, 12, 107, 37, 12, 61, 168, 2, 218, 56, 20, 25, 85, 75, 232, 163, 251, 101, 208, 254, 123, 187, 54, 92, 163, 249, 181, 2, 17, 0, 0, 0, 20, 117, 227, 240, 233, 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