Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c8f83b06902776f944d0b99c0b015c30f5e5710853b45c29637d8727751d573

Tx prefix hash: 4cf52e73cb7e440c6911e76da41a461ea5bafb9cf8b4108160248d02c83c6fb9
Tx public key: 9004008c576913f7a7cc6532ac36409d5ddd0b6b7d2a03f4d76b3ce910c8e2f8
Timestamp: 1706800891 Timestamp [UCT]: 2024-02-01 15:21:31 Age [y:d:h:m:s]: 01:135:18:26:54
Block: 948110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358050 RingCT/type: yes/0
Extra: 019004008c576913f7a7cc6532ac36409d5ddd0b6b7d2a03f4d76b3ce910c8e2f80211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490f2432ba51aacb3d05a393ff8cb5a4272b2335afcc815595679768f4ef5445 0.600000000000 1406482 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": 948120, "vin": [ { "gen": { "height": 948110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490f2432ba51aacb3d05a393ff8cb5a4272b2335afcc815595679768f4ef5445" } } ], "extra": [ 1, 144, 4, 0, 140, 87, 105, 19, 247, 167, 204, 101, 50, 172, 54, 64, 157, 93, 221, 11, 107, 125, 42, 3, 244, 215, 107, 60, 233, 16, 200, 226, 248, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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