Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8f800942a43ff626f87b81bee1f92e045e82d62b2f0d30c6565ef64c0fcc73

Tx prefix hash: e4698d7d33618dc117358f7970b239eaae7e140f526a8b7f9a30ba1382b9f80b
Tx public key: cca5f2e3b041a4f2c946397ead57b41dadb13fe4364a445468bccf8ba32d4eae
Timestamp: 1703280636 Timestamp [UCT]: 2023-12-22 21:30:36 Age [y:d:h:m:s]: 01:331:09:01:15
Block: 918941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495685 RingCT/type: yes/0
Extra: 01cca5f2e3b041a4f2c946397ead57b41dadb13fe4364a445468bccf8ba32d4eae0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2c1a1809f74c0da70be5bbffc98dae5e67a85c4af36115a9295f0c2e72d5e9 0.600000000000 1376605 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": 918951, "vin": [ { "gen": { "height": 918941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2c1a1809f74c0da70be5bbffc98dae5e67a85c4af36115a9295f0c2e72d5e9" } } ], "extra": [ 1, 204, 165, 242, 227, 176, 65, 164, 242, 201, 70, 57, 126, 173, 87, 180, 29, 173, 177, 63, 228, 54, 74, 68, 84, 104, 188, 207, 139, 163, 45, 78, 174, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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