Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0daf625a8a4c9b3114cd38d8e34606f81f95dda2d45908424efce29e621bf8ff

Tx prefix hash: ed7414c5eb0cc1d1c0d184cffb7acabd753bde3652682a96bde7a2e48f57777b
Tx public key: 831f8f9bb5aa457d77781850e66efc7589926a837f85143d6fe17854b5579fb6
Timestamp: 1720249374 Timestamp [UCT]: 2024-07-06 07:02:54 Age [y:d:h:m:s]: 00:269:19:59:10
Block: 1059623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192772 RingCT/type: yes/0
Extra: 01831f8f9bb5aa457d77781850e66efc7589926a837f85143d6fe17854b5579fb602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f59a005d79b8d1f014dbfcfcfba271d2c0160343f1d01c4c1de92ff04eb60e 0.600000000000 1530092 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": 1059633, "vin": [ { "gen": { "height": 1059623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f59a005d79b8d1f014dbfcfcfba271d2c0160343f1d01c4c1de92ff04eb60e" } } ], "extra": [ 1, 131, 31, 143, 155, 181, 170, 69, 125, 119, 120, 24, 80, 230, 110, 252, 117, 137, 146, 106, 131, 127, 133, 20, 61, 111, 225, 120, 84, 181, 87, 159, 182, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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