Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0755faca6257b5d904727edaec029e4e15f540ca8db664b598bbc2062ef1c1b7

Tx prefix hash: b025c1a7b90f607868a641ac29a50c114665c4eab705386bec579add205e3e3d
Tx public key: 244d8b48a44c4726644fc94928d2e66019f5f221e5f4e57c6a4fc79c59429f2e
Timestamp: 1704960291 Timestamp [UCT]: 2024-01-11 08:04:51 Age [y:d:h:m:s]: 01:045:08:54:34
Block: 932856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293495 RingCT/type: yes/0
Extra: 01244d8b48a44c4726644fc94928d2e66019f5f221e5f4e57c6a4fc79c59429f2e0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69d72fecaf45eaa865f6715ed4c856e27a98a8b5bc9bbecf5d55ffb9b4d1cfe7 0.600000000000 1390796 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": 932866, "vin": [ { "gen": { "height": 932856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69d72fecaf45eaa865f6715ed4c856e27a98a8b5bc9bbecf5d55ffb9b4d1cfe7" } } ], "extra": [ 1, 36, 77, 139, 72, 164, 76, 71, 38, 100, 79, 201, 73, 40, 210, 230, 96, 25, 245, 242, 33, 229, 244, 229, 124, 106, 79, 199, 156, 89, 66, 159, 46, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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