Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543fb4a5846e05df8b7d689c56f2d85f4d11cf7328a8b304b472ffabe0327722

Tx prefix hash: 8fedb9824b790b7f87d335d35f8d351f5438928b4bf8538b3357d0d645c12e4f
Tx public key: 1815f8e4f1b741056e3dfd273e6a45d527dc715817003579c0dd708fde85ac01
Timestamp: 1707307221 Timestamp [UCT]: 2024-02-07 12:00:21 Age [y:d:h:m:s]: 01:043:22:45:39
Block: 952317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292463 RingCT/type: yes/0
Extra: 011815f8e4f1b741056e3dfd273e6a45d527dc715817003579c0dd708fde85ac0102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b55007203d79265acdbe59491716e9b04abe9f820f98b482014df0a502cdf65b 0.600000000000 1411239 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": 952327, "vin": [ { "gen": { "height": 952317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b55007203d79265acdbe59491716e9b04abe9f820f98b482014df0a502cdf65b" } } ], "extra": [ 1, 24, 21, 248, 228, 241, 183, 65, 5, 110, 61, 253, 39, 62, 106, 69, 213, 39, 220, 113, 88, 23, 0, 53, 121, 192, 221, 112, 143, 222, 133, 172, 1, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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