Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 081614a62c271445bd6fd30abc1e003c4050d360199d2b45a967f20d5eaa15da

Tx prefix hash: cf52a908a9a60da44679d101498bd8658dd3cdb083c50d29a348a8268863f4ef
Tx public key: c51901f7d4aab1df10c16116ab1c1d541545bceaf365f4f48a243174f8393a24
Timestamp: 1699822116 Timestamp [UCT]: 2023-11-12 20:48:36 Age [y:d:h:m:s]: 01:142:23:35:56
Block: 890276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363363 RingCT/type: yes/0
Extra: 01c51901f7d4aab1df10c16116ab1c1d541545bceaf365f4f48a243174f8393a2402110000000157f93d59000000000000000000

1 output(s) for total of 0.688883906000 dcy

stealth address amount amount idx
00: 669b9c9fef4ce821c1db338021a1072de2066d530c3828b12e306987a6c6a035 0.688883906000 1346299 of 0

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": 890286, "vin": [ { "gen": { "height": 890276 } } ], "vout": [ { "amount": 688883906, "target": { "key": "669b9c9fef4ce821c1db338021a1072de2066d530c3828b12e306987a6c6a035" } } ], "extra": [ 1, 197, 25, 1, 247, 212, 170, 177, 223, 16, 193, 97, 22, 171, 28, 29, 84, 21, 69, 188, 234, 243, 101, 244, 244, 138, 36, 49, 116, 248, 57, 58, 36, 2, 17, 0, 0, 0, 1, 87, 249, 61, 89, 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