Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7471a3139f8774a3b04d52db7dc2b198390aebc7570bb3c733b54446eef505ca

Tx prefix hash: 95f7ac4a7f34cd759e2addb1cd42ee24ec209ce6cc0a2d9f9087443b4bf4284e
Tx public key: c8d15846045acde3b1244a4217ed21decba538e9df33d39e32c1e08461fd3f1c
Timestamp: 1722490690 Timestamp [UCT]: 2024-08-01 05:38:10 Age [y:d:h:m:s]: 00:269:07:46:11
Block: 1078201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192409 RingCT/type: yes/0
Extra: 01c8d15846045acde3b1244a4217ed21decba538e9df33d39e32c1e08461fd3f1c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1312b39f21ab50d0f8d25f5ad267292e7bf7ba96fb0b5c460c13670ebf83c2d1 0.600000000000 1550770 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": 1078211, "vin": [ { "gen": { "height": 1078201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1312b39f21ab50d0f8d25f5ad267292e7bf7ba96fb0b5c460c13670ebf83c2d1" } } ], "extra": [ 1, 200, 209, 88, 70, 4, 90, 205, 227, 177, 36, 74, 66, 23, 237, 33, 222, 203, 165, 56, 233, 223, 51, 211, 158, 50, 193, 224, 132, 97, 253, 63, 28, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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