Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53169d95697658e67981e15641a87b91097c783fc0d076c2dff5ebf212c79acf

Tx prefix hash: 1e14dc71e2e41c7e30c681b2ed4ae2c213176590586d5d5c3334be86b0385cae
Tx public key: d7303375010b7470556c4f573f87406c4785377bf0f39a208bc30d3f6fd1b9ac
Timestamp: 1710690564 Timestamp [UCT]: 2024-03-17 15:49:24 Age [y:d:h:m:s]: 01:030:13:56:58
Block: 980395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282828 RingCT/type: yes/0
Extra: 01d7303375010b7470556c4f573f87406c4785377bf0f39a208bc30d3f6fd1b9ac02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5cbb6e045b3101988fc30271917e0170b40796f33d1db6fc2f2f2e3a2bce399 0.600000000000 1440460 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": 980405, "vin": [ { "gen": { "height": 980395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5cbb6e045b3101988fc30271917e0170b40796f33d1db6fc2f2f2e3a2bce399" } } ], "extra": [ 1, 215, 48, 51, 117, 1, 11, 116, 112, 85, 108, 79, 87, 63, 135, 64, 108, 71, 133, 55, 123, 240, 243, 154, 32, 139, 195, 13, 63, 111, 209, 185, 172, 2, 17, 0, 0, 0, 12, 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