Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0827c04cf91b0a0d801529a2ce8ba5238ee95dd5566c7dd2d23d58ec73d09c1

Tx prefix hash: d0f0b8af08adb356dd6a40a3d165121e601cab720ad941d2209194e8b7dadb8d
Tx public key: 7f397897d7d663374748eeb95605e9901924135b7a87ba324b9049e026f948c5
Timestamp: 1718497986 Timestamp [UCT]: 2024-06-16 00:33:06 Age [y:d:h:m:s]: 00:210:13:21:36
Block: 1045119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150667 RingCT/type: yes/0
Extra: 017f397897d7d663374748eeb95605e9901924135b7a87ba324b9049e026f948c502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b4827738b49f20c8b4f0dc4860c9f62831e3e8393eb3530ae3e0700e38dd0f0 0.600000000000 1514608 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": 1045129, "vin": [ { "gen": { "height": 1045119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b4827738b49f20c8b4f0dc4860c9f62831e3e8393eb3530ae3e0700e38dd0f0" } } ], "extra": [ 1, 127, 57, 120, 151, 215, 214, 99, 55, 71, 72, 238, 185, 86, 5, 233, 144, 25, 36, 19, 91, 122, 135, 186, 50, 75, 144, 73, 224, 38, 249, 72, 197, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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