Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50df8ad343db5bf1798e39a12f46d8cb5ab838ebf540735f4fb87f730dbe405

Tx prefix hash: f348af37668e8519061615f362cea7f58543882ad914f64d0839c5692d044a82
Tx public key: 8d88e23e071777c996ea0fd967ae8bb0db1283e3d92f6cd5e0d560a061cafa53
Timestamp: 1719564451 Timestamp [UCT]: 2024-06-28 08:47:31 Age [y:d:h:m:s]: 01:141:15:11:04
Block: 1053944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359774 RingCT/type: yes/0
Extra: 018d88e23e071777c996ea0fd967ae8bb0db1283e3d92f6cd5e0d560a061cafa5302110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0050a7b1892f166f0a2f15945fa7c0db040147933141c4c7bba4dcf867d49224 0.600000000000 1524299 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": 1053954, "vin": [ { "gen": { "height": 1053944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0050a7b1892f166f0a2f15945fa7c0db040147933141c4c7bba4dcf867d49224" } } ], "extra": [ 1, 141, 136, 226, 62, 7, 23, 119, 201, 150, 234, 15, 217, 103, 174, 139, 176, 219, 18, 131, 227, 217, 47, 108, 213, 224, 213, 96, 160, 97, 202, 250, 83, 2, 17, 0, 0, 0, 10, 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