Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ae42cf2711045273f42bdfb98cd8a234d5589938b0de3fed2a40ab3d4bec1f

Tx prefix hash: 01bb2eeb02eb6311ae8708265a6cf2a631c0e907e85b4fd208a91054c21dc6d2
Tx public key: 5d689377e8452b3630365c8b4900bd1460feae844f6a667d1a97ee188953c8af
Timestamp: 1722452044 Timestamp [UCT]: 2024-07-31 18:54:04 Age [y:d:h:m:s]: 00:206:18:52:48
Block: 1077875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147659 RingCT/type: yes/0
Extra: 015d689377e8452b3630365c8b4900bd1460feae844f6a667d1a97ee188953c8af02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7234b6316a42521feff4cbe46e03ec74897fdbbf35310e0dfdce2237cb9f8d8 0.600000000000 1550430 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": 1077885, "vin": [ { "gen": { "height": 1077875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7234b6316a42521feff4cbe46e03ec74897fdbbf35310e0dfdce2237cb9f8d8" } } ], "extra": [ 1, 93, 104, 147, 119, 232, 69, 43, 54, 48, 54, 92, 139, 73, 0, 189, 20, 96, 254, 174, 132, 79, 106, 102, 125, 26, 151, 238, 24, 137, 83, 200, 175, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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