Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdba0832a5094b167b31da8b22215cc48e0c42a1fe97a787a15923b3e9261bbb

Tx prefix hash: 9887d0c17fa2cc2d3720b446776096c85cd27334c229eb2d33c9311ba633b656
Tx public key: cf234a712d04eb7beff99e95e0a37bcda6b54dcf5ed3a3e2e03f9e4bfa386b40
Timestamp: 1730560987 Timestamp [UCT]: 2024-11-02 15:23:07 Age [y:d:h:m:s]: 00:158:11:11:08
Block: 1145025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113097 RingCT/type: yes/0
Extra: 01cf234a712d04eb7beff99e95e0a37bcda6b54dcf5ed3a3e2e03f9e4bfa386b400211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a37f3d84580f2083dfe97d90330f514d9687c077e344addf63662eb8c0f49a 0.600000000000 1629386 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": 1145035, "vin": [ { "gen": { "height": 1145025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a37f3d84580f2083dfe97d90330f514d9687c077e344addf63662eb8c0f49a" } } ], "extra": [ 1, 207, 35, 74, 113, 45, 4, 235, 123, 239, 249, 158, 149, 224, 163, 123, 205, 166, 181, 77, 207, 94, 211, 163, 226, 224, 63, 158, 75, 250, 56, 107, 64, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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