Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f08b439b0a70da7409ad603cb7767d7441053a33e9244e8fb3f986a63eceb073

Tx prefix hash: 643ccd4b5898b9beb62d73725d2d2576a516fb89ba653ec94433504504dde05f
Tx public key: bc0db9a865509b0e999b74dd2e39e0f2450bf02e3fd19b7b8879f9b34f3acbd8
Timestamp: 1729172163 Timestamp [UCT]: 2024-10-17 13:36:03 Age [y:d:h:m:s]: 00:207:06:02:22
Block: 1133601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147918 RingCT/type: yes/0
Extra: 01bc0db9a865509b0e999b74dd2e39e0f2450bf02e3fd19b7b8879f9b34f3acbd802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74992663b74d90e463039f36f577a60228c99a91841c29eec58f7072c8ed7861 0.600000000000 1616770 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": 1133611, "vin": [ { "gen": { "height": 1133601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74992663b74d90e463039f36f577a60228c99a91841c29eec58f7072c8ed7861" } } ], "extra": [ 1, 188, 13, 185, 168, 101, 80, 155, 14, 153, 155, 116, 221, 46, 57, 224, 242, 69, 11, 240, 46, 63, 209, 155, 123, 136, 121, 249, 179, 79, 58, 203, 216, 2, 17, 0, 0, 0, 1, 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