Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbbb3cd22600f747d1b59a671c811a128a30c1891f776b812a8b7c66c28d1fd

Tx prefix hash: fcb01fb662271071d213a244fc4fe5539cd69e665670f3428b6365b9c1c4412f
Tx public key: f2b063ed8cbd96b3eb224c4d017c26111011f6d14dc550a3dfb78e65aaa8f92a
Timestamp: 1730635626 Timestamp [UCT]: 2024-11-03 12:07:06 Age [y:d:h:m:s]: 00:146:00:16:25
Block: 1145650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104180 RingCT/type: yes/0
Extra: 01f2b063ed8cbd96b3eb224c4d017c26111011f6d14dc550a3dfb78e65aaa8f92a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a518140da9113aeb3224f5c4ab14d3046eeb9f8d54d876970cb51237b1e9ea0 0.600000000000 1630133 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": 1145660, "vin": [ { "gen": { "height": 1145650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a518140da9113aeb3224f5c4ab14d3046eeb9f8d54d876970cb51237b1e9ea0" } } ], "extra": [ 1, 242, 176, 99, 237, 140, 189, 150, 179, 235, 34, 76, 77, 1, 124, 38, 17, 16, 17, 246, 209, 77, 197, 80, 163, 223, 183, 142, 101, 170, 168, 249, 42, 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