Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdde6ce67b8f0340c81a9c10f0e3e6ef048f6c93fba046ae44ba6219159375c8

Tx prefix hash: cd8d00443e7b17772feb5cdb6cce95f99c3ab8aa8d1c4bfcaae186d5f772276b
Tx public key: fd577f0a2a5db6dc756034ddb747e594e81b7d651d23d56366317fe4a3707ddb
Timestamp: 1727201976 Timestamp [UCT]: 2024-09-24 18:19:36 Age [y:d:h:m:s]: 00:192:16:55:53
Block: 1117265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137536 RingCT/type: yes/0
Extra: 01fd577f0a2a5db6dc756034ddb747e594e81b7d651d23d56366317fe4a3707ddb02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0a6a28b680aaf78bf1ecccac8835bd853890da72581c5f1d8bad30bef9da710 0.600000000000 1598042 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": 1117275, "vin": [ { "gen": { "height": 1117265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a6a28b680aaf78bf1ecccac8835bd853890da72581c5f1d8bad30bef9da710" } } ], "extra": [ 1, 253, 87, 127, 10, 42, 93, 182, 220, 117, 96, 52, 221, 183, 71, 229, 148, 232, 27, 125, 101, 29, 35, 213, 99, 102, 49, 127, 228, 163, 112, 125, 219, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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